Scaling service discovery in a micro-service environment

ABSTRACT

Systems and methods provide for scaling service discovery in a micro-service environment. A controller can inject a service discovery agent onto a host. At least one of the controller or the agent can identify a first set of micro-service containers that are dependencies of the first micro-service container and a second set of micro-service containers that are dependencies of the second micro-service container. At least one of the controller or the agent can update routing data for the first set of micro-service containers and the second set of micro-service containers. At least one of the controller or the agent can determine the second micro-service container has terminated on the host computing device. At least one of the controller or the agent can update the agent to remove the routing data for the second set of micro-service containers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of Ser. No. 17/817,568, filed on Aug.4, 2022, which in turn, is a Continuation of U.S. patent applicationSer. No. 16/505,618, filed on Jul. 8, 2019, now U.S. Pat. No. 11,412,053granted Aug. 9, 2022, which is a Continuation of U.S. patent applicationSer. No. 15/217,311, filed on Jul. 22, 2016, now U.S. Pat. No.10,348,838 granted Jul. 9, 2019, the contents of which are incorporatedherein by reference in their entireties.

TECHNICAL FIELD

This disclosure relates in general to the field of computer networksand, more particularly, pertains to scaling service discovery in amicro-service environment.

BACKGROUND

Container based micro-services is an architecture that is quickly beingadopted in the Data Center/Cloud Industry. Rather than build a singlemonstrous, monolithic application, container based micro-services splitthe application into a set of smaller interconnected micro-services. Inmicro-service architecture, service discovery plays a very importantrole, as container instances have dynamically assigned network locationsand change dynamically due to auto-scaling, failures and upgrades.Current systems utilize a server-side discovery load balancer that actsas a proxy to connect a container instance with other containerinstances providing micro-services. To make service discovery work,however, the proxy needs to track all container instances for eachmicro-service. In some instances, a single application can containhundreds of service and hundreds of container instances providing eachof the micro-services. As a result, in data center deploying multipleapplications, each server-side discovery load balancer or proxy may haveto track hundreds of thousands or even millions of container instances.Accordingly, improvements are needed.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited features andother advantages of the disclosure can be obtained, a more particulardescription of the principles briefly described above will be renderedby reference to specific embodiments thereof which are illustrated inthe appended drawings. Understanding that these drawings depict onlyexemplary embodiments of the disclosure and are not therefore to beconsidered to be limiting its scope, the principles herein are describedand explained with additional specificity and detail through the use ofthe accompanying drawings in which:

FIG. 1 illustrates an example network device according to some aspectsof the subject technology;

FIGS. 2A and 2B illustrate an example system embodiments according tosome aspects of the subject technology;

FIG. 3 illustrates a schematic block diagram of an example architecturefor a network fabric;

FIG. 4 illustrates an example overlay network;

FIGS. 5A-5D illustrate an example system configured to scale servicediscovery in a micro-service environment; and

FIG. 6 illustrates an example method of scaling service discovery in amicro-service environment.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology can bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a more thoroughunderstanding of the subject technology. However, it will be clear andapparent that the subject technology is not limited to the specificdetails set forth herein and may be practiced without these details. Insome instances, structures and components are shown in block diagramform in order to avoid obscuring the concepts of the subject technology.

Overview

Disclosed are systems, methods, and computer-readable storage media forscaling service discovery in a micro-service environment. A controllercan instantiate, on a host computing device, a first container instanceproviding a first micro-service of an application. The host computingdevice can include a service discovery agent. The controller canidentify a set of micro-services that are dependencies of the firstmicro-service, and update the service discovery agent with routing datafor container instances providing the set of micro-services that aredependencies of the first micro-service. The service discovery agent canuse the routing data to route requests from the first container instanceto container instances providing the set of micro-services that aredependencies of the first micro-service.

DETAILED DESCRIPTION

Disclosed are systems and methods for scaling service discovery in amicro-service environment. A brief introductory description of exemplarysystems and networks, as illustrated in FIGS. 1 through 4 , is disclosedherein, followed by a discussion of scaling service discovery in amicro-service environment. The disclosure now turns to FIG. 1 .

A computer network is a geographically distributed collection of nodesinterconnected by communication links and segments for transporting databetween endpoints, such as personal computers and workstations. Manytypes of networks are available, with the types ranging from local areanetworks (LANs) and wide area networks (WANs) to overlay andsoftware-defined networks, such as virtual extensible local areanetworks (VXLANs).

LANs typically connect nodes over dedicated private communications linkslocated in the same general physical location, such as a building orcampus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), or synchronous digital hierarchy (SDH) links. LANs andWANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.

The Internet is an example of a WAN that connects disparate networksthroughout the world, providing global communication between nodes onvarious networks. The nodes typically communicate over the network byexchanging discrete frames or packets of data according to predefinedprotocols, such as the Transmission Control Protocol/Internet Protocol(TCP/IP). In this context, a protocol can refer to a set of rulesdefining how the nodes interact with each other. Computer networks maybe further interconnected by an intermediate network node, such as arouter, to extend the effective “size” of each network.

Overlay networks generally allow virtual networks to be created andlayered over a physical network infrastructure. Overlay networkprotocols, such as Virtual Extensible LAN (VXLAN), NetworkVirtualization using Generic Routing Encapsulation (NVGRE), NetworkVirtualization Overlays (NVO3), and Stateless Transport Tunneling (STT),provide a traffic encapsulation scheme which allows network traffic tobe carried across L2 and L3 networks over a logical tunnel. Such logicaltunnels can be originated and terminated through virtual tunnel endpoints (VTEPs).

Moreover, overlay networks can include virtual segments, such as VXLANsegments in a VXLAN overlay network, which can include virtual L2 and/orL3 overlay networks over which virtual machines (VMs) and micro-servicecontainers communicate. The virtual segments can be identified through avirtual network identifier (VNI), such as a VXLAN network identifier,which can specifically identify an associated virtual segment or domain.

Network virtualization allows hardware and software resources to becombined in a virtual network. For example, network virtualization canallow multiple numbers of VMs and micro-service containers to beattached to the physical network via respective virtual LANs (VLANs).The VMs and micro-service containers can be grouped according to theirrespective VLAN, and can communicate with other VMs and micro-servicecontainers as well as other devices on the internal or external network.

Network segments, such as physical or virtual segments; networks;devices; ports; physical or logical links; and/or traffic in general canbe grouped into a bridge or flood domain. A bridge domain or flooddomain can represent a broadcast domain, such as an L2 broadcast domain.A bridge domain or flood domain can include a single subnet, but canalso include multiple subnets. Moreover, a bridge domain can beassociated with a bridge domain interface on a network device, such as aswitch. A bridge domain interface can be a logical interface whichsupports traffic between an L2 bridged network and an L3 routed network.In addition, a bridge domain interface can support internet protocol(IP) termination, VPN termination, address resolution handling, MACaddressing, etc. Both bridge domains and bridge domain interfaces can beidentified by a same index or identifier.

Furthermore, endpoint groups (EPGs) can be used in a network for mappingapplications to the network. In particular, EPGs can use a grouping ofapplication endpoints (e.g., micro-service containers) in a network toapply connectivity and policy to the group. EPGs can act as a containerfor buckets or collections of micro-service containers, applications, orapplication components, and tiers for implementing forwarding and policylogic. EPGs also allow separation of network policy, security, andforwarding from addressing by instead using logical applicationboundaries.

Cloud computing can also be provided in one or more networks to providecomputing services using shared resources. Cloud computing can generallyinclude Internet-based computing in which computing resources aredynamically provisioned and allocated to client or user computers orother devices on-demand, from a collection of resources available viathe network (e.g., “the cloud”). Cloud computing resources, for example,can include any type of resource, such as computing, storage, andnetwork devices, virtual machines (VMs), micro-service containers, etc.For instance, resources may include service devices (firewalls, deeppacket inspectors, traffic monitors, load balancers, etc.),compute/processing devices (servers, CPU's, memory, brute forceprocessing capability), storage devices (e.g., network attachedstorages, storage area network devices), etc. In addition, suchresources may be used to support virtual networks, virtual machines(VM), micro-service containers, databases, applications (Apps), etc.

Cloud computing resources may include a “private cloud,” a “publiccloud,” and/or a “hybrid cloud.” A “hybrid cloud” can be a cloudinfrastructure composed of two or more clouds that inter-operate orfederate through technology. In essence, a hybrid cloud is aninteraction between private and public clouds where a private cloudjoins a public cloud and utilizes public cloud resources in a secure andscalable manner. Cloud computing resources can also be provisioned viavirtual networks in an overlay network, such as a VXLAN.

FIG. 1 illustrates an exemplary network device 110 suitable forimplementing the present technology. Network device 110 includes amaster central processing unit (CPU) 162, interfaces 168, and a bus 115(e.g., a PCI bus). When acting under the control of appropriate softwareor firmware, the CPU 162 is responsible for executing packet management,error detection, and/or routing functions, such policy enforcement, forexample. The CPU 162 preferably accomplishes all these functions underthe control of software including an operating system and anyappropriate applications software. CPU 162 may include one or moreprocessors 163 such as a processor from the Motorola family ofmicroprocessors or the MIPS family of microprocessors. In an alternativeembodiment, processor 163 is specially designed hardware for controllingthe operations of network device 110. In a specific embodiment, a memory161 (such as non-volatile RAM and/or ROM) also forms part of CPU 162.However, there are many different ways in which memory could be coupledto the system.

The interfaces 168 are typically provided as interface cards (sometimesreferred to as “line cards”). Generally, they control the sending andreceiving of data packets over the network and sometimes support otherperipherals used with the network device 110. Among the interfaces thatmay be provided are Ethernet interfaces, frame relay interfaces, cableinterfaces, DSL interfaces, token ring interfaces, and the like. Inaddition, various very high-speed interfaces may be provided such asfast token ring interfaces, wireless interfaces, Ethernet interfaces,Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POSinterfaces, FDDI interfaces and the like. Generally, these interfacesmay include ports appropriate for communication with the appropriatemedia. In some cases, they may also include an independent processorand, in some instances, volatile RAM. The independent processors maycontrol such communications intensive tasks as packet switching, mediacontrol, and management. By providing separate processors for thecommunications intensive tasks, these interfaces allow the mastermicroprocessor 162 to efficiently perform routing computations, networkdiagnostics, security functions, etc.

Although the system shown in FIG. 1 is one specific network device ofthe present technology, it is by no means the only network devicearchitecture on which the present technology can be implemented. Forexample, an architecture having a single processor that handlescommunications as well as routing computations, etc. is often used.Further, other types of interfaces and media could also be used with thenetwork device.

Regardless of the network device's configuration, it may employ one ormore memories or memory modules (including memory 161) configured tostore program instructions for the general-purpose network operationsand mechanisms for roaming, route optimization and routing functionsdescribed herein. The program instructions may control the operation ofan operating system and/or one or more applications, for example. Thememory or memories may also be configured to store tables such asmobility binding, registration, and association tables, etc.

FIG. 2A, and FIG. 2B illustrate exemplary possible system embodiments.The more appropriate embodiment will be apparent to those of ordinaryskill in the art when practicing the present technology. Persons ofordinary skill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 2A illustrates a conventional system bus computing systemarchitecture 200 wherein the components of the system are in electricalcommunication with each other using a bus 205. Exemplary system 200includes a processing unit (CPU or processor) 210 and a system bus 205that couples various system components including the system memory 215,such as read only memory (ROM) 220 and random access memory (RAM) 225,to the processor 210. The system 200 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 210. The system 200 can copy data from the memory215 and/or the storage device 230 to the cache 212 for quick access bythe processor 210. In this way, the cache can provide a performanceboost that avoids processor 210 delays while waiting for data. These andother modules can control or be configured to control the processor 210to perform various actions. Other system memory 215 may be available foruse as well. The memory 215 can include multiple different types ofmemory with different performance characteristics. The processor 210 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 232, module 2 234, and module 3 236 stored instorage device 230, configured to control the processor 210 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 210 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 200, an inputdevice 245 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 235 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 200. The communications interface240 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 230 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 225, read only memory (ROM) 220, andhybrids thereof.

The storage device 230 can include software modules 232, 234, 236 forcontrolling the processor 210. Other hardware or software modules arecontemplated. The storage device 230 can be connected to the system bus205. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 210, bus 205, output device 235, andso forth, to carry out the function.

FIG. 2B illustrates a computer system 250 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 250 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 250 can include a processor255, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 255 cancommunicate with a chipset 260 that can control input to and output fromprocessor 255. In this example, chipset 260 outputs information tooutput 265, such as a display, and can read and write information tostorage device 270, which can include magnetic media, and solid statemedia, for example. Chipset 260 can also read data from and write datato RAM 275. A bridge 280 for interfacing with a variety of userinterface components 285 can be provided for interfacing with chipset260. Such user interface components 285 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 250 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 260 can also interface with one or more communication interfaces290 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 255 analyzing data stored in storage 270 or RAM 275.Further, the machine can receive inputs from a user via user interfacecomponents 285 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 255.

It can be appreciated that exemplary systems 200 and 250 can have morethan one processor 210 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

FIG. 3 illustrates a schematic block diagram of an example architecture300 for a network fabric 312. The network fabric 312 can include spineswitches 302A, 302B, . . . , 302N (collectively “302”) connected to leafswitches 304 _(A), 304 _(B), 304 _(C) . . . 304 _(N) (collectively“304”) in the network fabric 312.

Spine switches 302 can be L3 switches in the fabric 312. However, insome cases, the spine switches 302 can also, or otherwise, perform L2functionalities. Further, the spine switches 302 can support variouscapabilities, such as 40 or 10 Gbps Ethernet speeds. To this end, thespine switches 302 can include one or more 40 Gigabit Ethernet ports.Each port can also be split to support other speeds. For example, a 40Gigabit Ethernet port can be split into four 10 Gigabit Ethernet ports.

In some embodiments, one or more of the spine switches 302 can beconfigured to host a proxy function that performs a lookup of theendpoint address identifier to locator mapping in a mapping database onbehalf of leaf switches 304 that do not have such mapping. The proxyfunction can do this by parsing through the packet to the encapsulatedtenant packet to get to the destination locator address of the tenant.The spine switches 302 can then perform a lookup of their local mappingdatabase to determine the correct locator address of the packet andforward the packet to the locator address without changing certainfields in the header of the packet.

When a packet is received at a spine switch 302 _(i), the spine switch302 _(i) can first check if the destination locator address is a proxyaddress. If so, the spine switch 302 _(i) can perform the proxy functionas previously mentioned. If not, the spine switch 302 _(i) can look upthe locator in its forwarding table and forward the packet accordingly.

Spine switches 302 connect to leaf switches 304 in the fabric 312. Leafswitches 304 can include access ports (or non-fabric ports) and fabricports. Fabric ports can provide uplinks to the spine switches 302, whileaccess ports can provide connectivity for devices, hosts, endpoints,VMs, micro-service containers, or external networks to the fabric 312.

Leaf switches 304 can reside at the edge of the fabric 312, and can thusrepresent the physical network edge. In some cases, the leaf switches304 can be top-of-rack (“ToR”) switches configured according to a ToRarchitecture. In other cases, the leaf switches 304 can be aggregationswitches in any particular topology, such as end-of-row (EoR) ormiddle-of-row (MoR) topologies. The leaf switches 304 can also representaggregation switches, for example.

The leaf switches 304 can be responsible for routing and/or bridging thedata packets and applying network policies. In some cases, a leaf switchcan perform one or more additional functions, such as implementing amapping cache, sending packets to the proxy function when there is amiss in the cache, encapsulating packets, enforcing ingress or egresspolicies, etc.

Moreover, the leaf switches 304 can contain virtual switchingfunctionalities, such as a virtual tunnel endpoint (VTEP) function asexplained below in the discussion of VTEP 408 in FIG. 4 . To this end,leaf switches 304 can connect the fabric 312 to an overlay network, suchas overlay network 400 illustrated in FIG. 4 .

Network connectivity in the fabric 312 can flow through the leafswitches 304. Here, the leaf switches 304 can provide servers,resources, endpoints, external networks, micro-service containers or VMsaccess to the fabric 312, and can connect the leaf switches 304 to eachother. In some cases, the leaf switches 304 can connect EPGs to thefabric 312 and/or any external networks. Each EPG can connect to thefabric 312 via one of the leaf switches 304, for example.

Endpoints 310A-E (collectively “310”) can connect to the fabric 312 vialeaf switches 304. For example, endpoints 310A and 310B can connectdirectly to leaf switch 304A, which can connect endpoints 310A and 310Bto the fabric 312 and/or any other one of the leaf switches 304.Similarly, endpoint 310E can connect directly to leaf switch 304C, whichcan connect endpoint 310E to the fabric 312 and/or any other of the leafswitches 304. On the other hand, endpoints 310C and 310D can connect toleaf switch 304B via L2 network 306. Similarly, the wide area network(WAN) can connect to the leaf switches 304C or 304D via L3 network 308.

Endpoints 310 can include any communication device, such as a computer,a server, a switch, a router, etc. In some cases, the endpoints 310 caninclude a server, hypervisor, or switch configured with a VTEPfunctionality which connects an overlay network, such as overlay network400 below, with the fabric 312. For example, in some cases, theendpoints 310 can represent one or more of the VTEPs 408A-D illustratedin FIG. 4 . Here, the VTEPs 408A-D can connect to the fabric 312 via theleaf switches 304. The overlay network can host physical devices, suchas servers, applications, EPGs, virtual segments, virtual workloads,etc. In addition, the endpoints 310 can host virtual workload(s),clusters, and applications or services, which can connect with thefabric 312 or any other device or network, including an externalnetwork. For example, one or more endpoints 310 can host, or connect to,a cluster of load balancers or an EPG of various applications.

Although the fabric 312 is illustrated and described herein as anexample leaf-spine architecture, one of ordinary skill in the art willreadily recognize that the subject technology can be implemented basedon any network fabric, including any data center or cloud networkfabric. Indeed, other architectures, designs, infrastructures, andvariations are contemplated herein.

FIG. 4 illustrates an exemplary overlay network 400. Overlay network 400uses an overlay protocol, such as VXLAN, NVGRE, NVO3, or STT, toencapsulate traffic in L2 and/or L3 packets which can cross overlay L3boundaries in the network. As illustrated in FIG. 4 , overlay network400 can include hosts 406A-D interconnected via network 402.

Network 402 can include a packet network, such as an IP network, forexample. Moreover, network 402 can connect the overlay network 400 withthe fabric 312 in FIG. 3 . For example, VTEPs 408A-D can connect withthe leaf switches 304 in the fabric 312 via network 402.

Hosts 406A-D include virtual tunnel end points (VTEP) 408A-D, which canbe virtual nodes or switches configured to encapsulate andde-encapsulate data traffic according to a specific overlay protocol ofthe network 400, for the various virtual network identifiers (VNIDs)410A-I. Moreover, hosts 406A-D can include servers containing a VTEPfunctionality, hypervisors, and physical switches, such as L3 switches,configured with a VTEP functionality. For example, hosts 406A and 406Bcan be physical switches configured to run VTEPs 408A-B. Here, hosts406A and 406B can be connected to servers 404A-D, which, in some cases,can include virtual workloads through micro-service container or VMsloaded on the servers, for example.

In some embodiments, network 400 can be a VXLAN network, and VTEPs408A-D can be VXLAN tunnel end points (VTEP). However, as one ofordinary skill in the art will readily recognize, network 400 canrepresent any type of overlay or software-defined network, such asNVGRE, STT, or even overlay technologies yet to be invented.

The VNIDs can represent the segregated virtual networks in overlaynetwork 400. Each of the overlay tunnels (VTEPs 408A-D) can include oneor more VNIDs. For example, VTEP 408A can include VNIDs 1 and 2, VTEP408B can include VNIDs 1 and 2, VTEP 408C can include VNIDs 1 and 2, andVTEP 408D can include VNIDs 1-3. As one of ordinary skill in the artwill readily recognize, any particular VTEP can, in other embodiments,have numerous VNIDs, including more than the 3 VNIDs illustrated in FIG.4 .

The traffic in overlay network 400 can be segregated logically accordingto specific VNIDs. This way, traffic intended for VNID 1 can be accessedby devices residing in VNID 1, while other devices residing in otherVNIDs (e.g., VNIDs 2 and 3) can be prevented from accessing suchtraffic. In other words, devices or endpoints connected to specificVNIDs can communicate with other devices or endpoints connected to thesame specific VNIDs, while traffic from separate VNIDs can be isolatedto prevent devices or endpoints in other specific VNIDs from accessingtraffic in different VNIDs.

Servers 404A-D and VMs 404E-I can connect to their respective VNID orvirtual segment, and communicate with other servers or VMs residing inthe same VNID or virtual segment. For example, server 404A cancommunicate with server 404C and VMs 404E and 404G because they allreside in the same VNID, viz., VNID 1. Similarly, server 404B cancommunicate with VMs 404F and 404H because they all reside in VNID 2.VMs 404E-I can host virtual workloads, which can include applicationworkloads, resources, and services, for example. However, in some cases,servers 404A-D can similarly host virtual workloads through VMs hostedon the servers 404A-D. Moreover, each of the servers 404A-D and VMs404E-I can represent a single server or VM, but can also representmultiple servers or VMs, such as a cluster of servers or VMs.

VTEPs 408A-D can encapsulate packets directed at the various VNIDs 1-3in the overlay network 400 according to the specific overlay protocolimplemented, such as VXLAN, so traffic can be properly transmitted tothe correct VNID and recipient(s). Moreover, when a switch, router, orother network device receives a packet to be transmitted to a recipientin the overlay network 400, it can analyze a routing table, such as alookup table, to determine where such packet needs to be transmitted sothe traffic reaches the appropriate recipient. For example, if VTEP 408Areceives a packet from endpoint 404B that is intended for endpoint 404H,VTEP 408A can analyze a routing table that maps the intended endpoint,endpoint 404H, to a specific switch that is configured to handlecommunications intended for endpoint 404H. VTEP 408A might not initiallyknow, when it receives the packet from endpoint 404B, that such packetshould be transmitted to VTEP 408D in order to reach endpoint 404H.Accordingly, by analyzing the routing table, VTEP 408A can lookupendpoint 404H, which is the intended recipient, and determine that thepacket should be transmitted to VTEP 408D, as specified in the routingtable based on endpoint-to-switch mappings or bindings, so the packetcan be transmitted to, and received by, endpoint 404H as expected.

However, continuing with the previous example, in many instances, VTEP408A may analyze the routing table and fail to find any bindings ormappings associated with the intended recipient, e.g., endpoint 404H.Here, the routing table may not yet have learned routing informationregarding endpoint 404H. In this scenario, the VTEP 408A may likelybroadcast or multicast the packet to ensure the proper switch associatedwith endpoint 404H can receive the packet and further route it toendpoint 404H.

In some cases, the routing table can be dynamically and continuouslymodified by removing unnecessary or stale entries and adding new ornecessary entries, in order to maintain the routing table up-to-date,accurate, and efficient, while reducing or limiting the size of thetable.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

Depending on the desired implementation in the network 400, a variety ofnetworking and messaging protocols may be used, including but notlimited to TCP/IP, open systems interconnection (OSI), file transferprotocol (FTP), universal plug and play (UpnP), network file system(NFS), common internet file system (CIFS), AppleTalk etc. As would beappreciated by those skilled in the art, the network 400 illustrated inFIG. 4 is used for purposes of explanation, a network system may beimplemented with many variations, as appropriate, in the configurationof network platform in accordance with various embodiments of thepresent disclosure.

Having disclosed a brief introductory description of exemplary systemsand networks, the discussion now turns to scaling service discovery in amicro-service environment. Rather than build a single monstrous,monolithic application, container based micro-services split theapplication into a set of smaller interconnected micro-services.Multiple container instances can be instantiated to provide the variousmicro-services, allowing the application to be easily scaled as needed.Each instantiated container instance can be assigned its own IP addressand port number and distributed throughout a data center on variousnodes in the network. The IP addresses and port numbers can be used toprovide network based communications between the container instances toprovide the application.

A server-side service discovery agent can be used to managecommunications between the container instances. A host node can includea service discovery agent that acts as a load balancer/proxy to connecta container instance on the host node with other container instancesproviding other micro-services of the application. The service discoveryagent on a host can receive and direct packets to and from the containerinstances. The service discovery agent can maintain routing data (e.g.,IP addresses and port values) for other container instances in thenetwork, which can be used to route received requests to an appropriatecontainer instance.

To reduce the number of container instances that need to be tracked by aservice discovery agent, a controller in the network can be configuredto update the service discovery agent to either provide new routing dataor remove routing data based on the container instances on the hostnode. For example, the controller can update the service discovery agentto only include routing data for container instances providingmicro-services that are dependencies of micro-services provided bycontainer instances instantiated on the host node. Accordingly, aservice discovery agent will not include unnecessary routing data,thereby reducing memory usage and increasing throughput.

FIGS. 5A-5D illustrate an example system configured to scale servicediscovery in a micro-service environment. As shown, in FIG. 5A, system500 includes controller 502 and host computing device 504. Controller500 and host computing device 504 can be any type of computing device,node, VM, etc., in a network. Although controller 502 and host computingdevice 504 are shown as separate entities, in some embodimentscontroller 502 and host computing device 504 can reside on the samecomputing device. For example, controller 502 can reside on hostcomputing device 504.

Host computing device 504 can be configured to host one or morecontainer instances, each providing a micro-service. Each containerinstance can be assigned a unique IP address and port number to allowfor network based communication between the container instancesdistributed throughout the network.

Host computing device 504 can include service discovery agent 506configured to manage communications between container instances includedon host computing device 504 and other container instances distributedthroughout the network. For example, service discovery agent 506 can bea load balancer and/or proxy configured to inspect and direct packets toand from the container instances. For example, local container instanceson host computing device 504 can transmit requests that are inspected byservice discovery agent 506 and service discovery agent 506 can thenroute the requests to an appropriate container instance in the network.To accomplish this, service discovery agent 506 can maintain routingdata (e.g., IP address and port values) for other container instances inthe network, which can be used to route requests to an appropriatecontainer instance.

Controller 502 can be configured to update service discovery agent 506to reduce the amount of routing data maintained by service discoveryagent 506. Some micro-services of an application may be related to othermicro-services of the application that are dependencies. For instance,some micro-services may require the functionality of one or moremicro-services and may need to make Application Programming Interface(API) calls to those micro-services as part of their functioning. As anexample, a micro-service providing a payment functionality of anapplication may require the use of another micro-service providing anotification functionality to notify a user that a payment has beencompleted. Accordingly, the notification micro-service is a dependencyof the payment micro-service.

While a micro-service may be related to a set of one or more othermicro-services that are dependencies of the micro-service, this is notthe case for all micro-services of an application. Some micro-servicesmay not have any dependencies. Further, a micro-service may only berelated to a subset of the total micro-services of an application,meaning that not all micro-services are dependencies of each other.Accordingly, service discovery agent 506 only needs to maintain routingdata for container instances that provide micro-services that aredependencies of micro-services provided by container instances on hostcomputing device 504.

Controller 502 can be configured to update service discovery agent 506to include only the routing data necessary based on the containerinstances on host computing device 504. For example, in response to acontainer instance being instantiated on host computing device 504,controller 502 can determine a set of micro-services that aredependencies of the micro-service provided by the newly instantiatedcontainer instance, and then update service discovery agent 506 withrouting data for container instances providing the set ofmicro-services. Likewise, in response to a container instance beingremoved from host computing device 504, controller 502 can updateservice discovery agent 506 to remove routing data for containerinstances that are dependencies of the micro-service provided by theremoved container instance. For example, controller 502 can check theremaining container instances and determine their correspondingdependencies. Controller 502 can then update the routing dataaccordingly.

In some embodiments, controller 502 can maintain a micro-servicedependencies table that identifies the dependencies for a particularapplication. In response to determining that a container instance hasbeen added or removed from host computing device 504, controller 502 cansearch the micro-service dependency table to identify the set ofmicro-services that are dependencies of the micro-service provided bythe added or removed container instance. Alternatively, in someembodiments, container instances providing a specific micro-service canall be added to an end point group and associated with a group basedpolicy defining the micro-services that are dependencies. In response todetermining that a container instance has been added or removed fromhost computing device 504, controller 502 can gather the set ofmicro-services that are dependencies of the micro-service based on thegroup based policy associated with the container instance that was addedor removed.

FIG. 5B shows system 500 after a container instance has beeninstantiated on host computing device 504. As shown, container instance508 has been instantiated on host computing device 504. Containerinstance 508 can be providing micro-service 1. As further shown,controller 502 has updated service discovery agent 506 to includerouting data for container instances 510, which provide a set ofmicro-services that are dependencies of micro-service 1, provided bycontainer instance 508. To utilize a micro-service provided by one ofcontainer instances 510, container instance 508 can communicate withservice discovery agent 506, which acts as load balancer and/or proxyand routes the request to one of container instances 510.

FIG. 5C shows system 500 after a second container instance has beeninstantiated on host computing device 504. As shown, container instance512 has been instantiated on container instance 504. Container instance512 can provide micro-service 2. Further, controller 502 has updatedservice discovery agent 506 to include routing data for containerinstances 514 that provide micro-services that are dependencies ofmicro-service 2. In some instances, micro-service 1 and micro-service 2may both share certain dependencies. Accordingly, upon containerinstance 512 being instantiated on host computing device 504, controller502 can identify a subset of micro-services that are dependencies ofmicro-service 2 that are not included in the set of micro-services thatare dependencies of micro-service 1, provided by container instance 508.Because service discovery agent 506 already has routing data forcontainer instances providing any micro services that are dependenciesof both micro-service 1 and micro-service 2, controller 502 can updateservice discovery agent 506 with routing data for the subset ofmicro-services that are dependencies of micro-service 2 that are notincluded in the set of micro-services that are dependencies ofmicro-service 1.

FIG. 5D shows system 500 after a container instance has been removedfrom host computing device 504. As shown, container instance 510 hasbeen removed form host computing device 504. Further, controller 502 hasremoved container instances 514, which provide services that aredependencies of micro-service 2 but are not dependencies ofmicro-service 1. Routing data for container instances that providemicro-services for both micro-service 1 and micro-service 2 can bemaintained by service discovery agent 506 to continue servicingcontainer instance 508.

FIG. 6 illustrates an example method 600 of scaling service discovery ina micro-service environment. It should be understood that there can beadditional, fewer, or alternative steps performed in similar oralternative orders, or in parallel, within the scope of the variousembodiments unless otherwise stated.

At step 602, a controller can instantiate, on a host computing device, afirst container instance providing a first micro-service of anapplication. The host computing device can include a service discoveryagent configured to manage communications between the first containerinstance and container instances on other host computing devices.

At step 604, the controller can identify a set of micro-services thatare dependencies of the first micro-service. For example, the hostcontroller can search a micro-service dependencies table of theapplication for the set of micro-services that are dependencies of thefirst micro-service. The micro-service dependencies table can listmicro-services of the application and their corresponding dependencies.

As another example, the controller can gather the set of micro-servicesthat are dependencies of the first micro-service from a group basedpolicy associated with an end point group to which the first containerinstance is assigned. The end point group can include only containerinstances providing the first micro-service and the group based policycan identify dependencies of the first micro-service.

At step 606, the controller can update the service discovery agent withrouting data for container instances providing the set of micro-servicesthat are dependencies of the first micro-service. The service discoveryagent can use the routing data to route requests from the firstcontainer instance to container instances providing the set ofmicro-services that are dependencies of the first micro-service.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, rackmount devices, standalone devices, and so on.Functionality described herein also can be embodied in peripherals oradd-in cards. Such functionality can also be implemented on a circuitboard among different chips or different processes executing in a singledevice, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims. Moreover, claimlanguage reciting “at least one of” a set indicates that one member ofthe set or multiple members of the set satisfy the claim.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Note that in certain example implementations, the optimization and/orplacement functions outlined herein may be implemented by logic encodedin one or more tangible, non-transitory media (e.g., embedded logicprovided in an application specific integrated circuit [ASIC], digitalsignal processor [DSP] instructions, software [potentially inclusive ofobject code and source code] to be executed by a processor, or othersimilar machine, etc.). The computer-readable storage devices, mediums,and memories can include a cable or wireless signal containing a bitstream and the like. However, when mentioned, non-transitorycomputer-readable storage media expressly exclude media such as energy,carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1. (canceled)
 2. A computer-implemented method comprising: establishing,by a controller, a service discovery agent associated with a firstmicroservice of a plurality of microservices associated with adistributed application, the first microservice being provided by one ormore containers associated with the first microservice, wherein theservice discovery agent manages communications associated with the firstmicroservice; instantiating a second microservice that is a dependencyof the first microservice and a third microservice that is not adependency of the first microservice, wherein the second microservice isprovided by one or more containers associated with the secondmicroservice; providing, by the controller, routing data associated withthe second microservice to the service discovery agent associated withthe first microservice; determining, by the controller, that at leastone container of the one or more containers associated with the secondmicroservice has terminated; providing updated routing data associatedwith the second microservice to the service discovery agent; andupdating, at the service discovery agent, the routing data associatedwith the second microservice.
 3. The computer-implemented method ofclaim 2, wherein the service discovery agent is located on a first hostin a first cloud.
 4. The computer-implemented method of claim 2, furthercomprising: load-balancing requests to the one or more containersproviding the plurality of microservices.
 5. The computer-implementedmethod of claim 2, further comprising: checking for dependencies of thefirst microservice.
 6. The computer-implemented method of claim 2,wherein providing the routing data associated with the secondmicroservice to the service discovery agent associated with the firstmicroservice excludes routing data associated with the thirdmicroservice.
 7. The computer-implemented method of claim 2, whereinupdating the routing data associated with the second microservicecomprises removing the routing data associated with the secondmicroservice.
 8. A system, comprising: one or more processors, andmemory including instructions that, when executed by the one or moreprocessors, cause the system to: establish by a controller, a servicediscovery agent associated with a first microservice of a plurality ofmicroservices associated with a distributed application, the firstmicroservice being provided by one or more containers associated withthe first microservice, wherein the service discovery agent managescommunications associated with the first microservice; instantiate asecond microservice that is a dependency of the first microservice and athird microservice that is not a dependency of the first microservice,wherein the second microservice is provided by one or more containersassociated with the second microservice; provide, by the controller,routing data associated with the second microservice to the servicediscovery agent associated with the first microservice; determine, bythe controller, that at least one container of the one or morecontainers associated with the second microservice has terminated;provide updated routing data associated with the second microservice tothe service discovery agent; and update, at the service discovery agent,the routing data associated with the second microservice.
 9. The systemof claim 8, wherein the service discovery agent is located on a firsthost in a first cloud.
 10. The system of claim 8, further comprisingfurther instructions that, when executed by the one or more processors,causes the one or more processors to: load-balance requests to the oneor more containers providing the plurality of microservices.
 11. Thesystem of claim 8, further comprising further instructions that, whenexecuted by the one or more processors, causes the one or moreprocessors to: check for dependencies of the first microservice.
 12. Thesystem of claim 8, wherein providing the routing data associated withthe second microservice to the service discovery agent associated withthe first microservice excludes routing data associated with the thirdmicroservice.
 13. The system of claim 8, wherein updating the routingdata associated with the second microservice comprises removing therouting data associated with the second microservice.
 14. Anon-transitory computer-readable medium storing instructions that, whenexecuted by one or more processors, cause the processors to: establishby a controller, a service discovery agent associated with a firstmicroservice of a plurality of microservices associated with adistributed application, the first microservice being provided by one ormore containers associated with the first microservice, wherein theservice discovery agent manages communications associated with the firstmicroservice; instantiate a second microservice that is a dependency ofthe first microservice and a third microservice that is not a dependencyof the first microservice, wherein the second microservice is providedby one or more containers associated with the second microservice;provide, by the controller, routing data associated with the secondmicroservice to the service discovery agent associated with the firstmicroservice; determine, by the controller, that at least one containerof the one or more containers associated with the second microservicehas terminated; provide updated routing data associated with the secondmicroservice to the service discovery agent; and update, at the servicediscovery agent, the routing data associated with the secondmicroservice.
 15. The non-transitory computer-readable medium of claim14, wherein the service discovery agent is located on a first host in afirst cloud.
 16. The non-transitory computer-readable medium of claim14, further comprising instructions that, when executed by the one ormore processors, causes the one or more processors to: load-balancerequests to the one or more containers providing the plurality ofmicroservices.
 17. The non-transitory computer-readable medium of claim14, further comprising instructions that, when executed by the one ormore processors, causes the one or more processors to: check fordependencies of the first microservice.
 18. The non-transitorycomputer-readable medium system of claim 14, wherein providing therouting data associated with the second microservice to the servicediscovery agent associated with the first microservice excludes routingdata associated with the third microservice.
 19. The non-transitorycomputer-readable medium system of claim 14, wherein updating therouting data associated with the second microservice comprises removingthe routing data associated with the second microservice.